-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
provider/kubernetes: Upgrade K8S to 1.6.1 #14923
Conversation
hrm, 🤔 but these packages are supposed to be missing in the new version... |
12daf8b
to
40c6d9b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Why
Although we wanted to avoid the upgrade until we ship all
v1
resources we discovered a slightly annoying behaviour in pod - specifically kubelet automounting secrets by default. It is possible to turn off that behaviour in 1.6 and avoid spurious diffs and generally avoid the complexity of figuring out what's default (automounted) and what was defined by the user.TL;DR To unblock #13571
How did it go?
I tried upgrading to the latest stable version (1.6.4) but I was unable to put all the dependency puzzle pieces together. Apparently the K8S project decided to split the main repo into multiple different ones and they seem to be in some kind of transition phase still which makes vendoring a nontrivial task especially due to the way the main k8s project does vendoring for other k8s projects.
The commit messages should be self-explanatory.
Test plan